-
Notifications
You must be signed in to change notification settings - Fork 167
Move parameters and conversion functions to their own packages #2189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Move parameters and conversion functions to their own packages #2189
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: julianKatz The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
097769e
to
eac2b7f
Compare
61ea5ba
to
976bdb9
Compare
976bdb9
to
6343685
Compare
bf688b8
to
b3393ff
Compare
@julianKatz: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
What type of PR is this?
What this PR does / why we need it:
This PR is a follow-up to #2186.
This PR moves the parsing of parameters into their own package:
pkg/parameters
. This is a lot of logic and worthy of its own package.Along the way, I found that
pkg/common
had a number of conversion helper functions (Convert.*
) that were public and occasionally used by both parameters.go and other files, and sometimes only parameters.go. Several of them also had their own unit tests already. Thus, I thought this was also worthy of its own package. This PR thus addspkg/convert
.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: